Platypus Integration

Introduction

Issuetracker has built-in capability to communication with the Platypus API service on version 6.1 - 7.0. This implements the Issuetracker Billing Hooks (the ability to search Platypus users instead of only local Issuetracker users) and the Ticket Export APIs.

Required Information for setup:

  • External IP - We will need to know the external IP address of the server. All requests will come from the serverplus IPs:
    • 209.90.90.162
    • 209.90.90.165
    • 173.10.22.121

    Firewall rules, both on the windows machine running the API service and any firewalls/routers afterwards, will need to allow traffic from these IPs on the API service port. The Platypus API servcie defaults to use port 5566 for SSL and 5565 without SSL.

  • Port - From the “Platypus API Configuration” [1] we need the port (if other than 0, the default) and whether ‘Enable SSL’ is checked.

  • Platypus account (username/password) - This platypus staff user needs to have permissions to create tickets from the web interface (Maintenance -> Security, Security Assignments) [2] and only needs visibility to companies that we are doing support for.

This information can be sent to your account rep, or to it@serverplus.com

[1]
../_images/api_settings.png
[2]
../_images/staff_security.png